2014-04-16-8009 - Spec - EMEA POS FICO Journal Entry Creation #EMEA #ABAP #FIOutgoingpayments #FIIncomingPayments
SPECIFICATIONS
8009 - EMEA POS FICO Journal Entry Creation
Purpose
EMEA POS FICO Journal Entry Creation
Admin Info
Purpose
|
EMEA POS FICO Journal Entry Creation
|
Requested By
|
Jingsha Brennan
|
Spec Created By
|
Venkat
|
Spec Created Date
|
05/04/2014
|
Spec QA by
|
Venkat
|
Objects
|
Program - ZFI_POST_GL_ENTRIES,
Table - ZFIRPGL,
Tcode - ZPOSEMEA
|
Document Status
|
Cpmpleted
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
08
|
2
|
Documentation
|
08
|
3
|
Development/ Config
|
40
|
4
|
Unit test in DEV
|
12
|
5
|
Unit test in QUA
|
12
|
6
|
Other activity
|
|
|
TOTAL
|
80
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
Documents
[Attach any document(s) received for the requirement(s)]
EMEA POS functional Spec-draft (2).docx
Custom Table EMEA POS.xlsx
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
The EMEA POS system will provide information in certain format and a customized program should be developed to read this information and create journal entries in SAP automatically (Number 3 in below process). The journal entries are created to capture Retail Revenue, Cost of Goods Sold, Inventory movement that is related to sales, accounts receivables as well as the inventory movements that are not related to retail sales.
Process Flow Diagram (SD Delivery and Billing)
In Scope:
[List the
activities to be included in s
cope]
Develop the following Objects,
- Custom table to Maintain Inventory Activity Details of Inventory Details related Retail Sales and Non Retail Sales.
- Program to create Journal Entries from Input File
Out of Scope:
[Out of scope activities]
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
Develop a custom Table
Develop a Program to Create Journal Entries with Following Selection Parameter,
1) Radio Buttons For either Retail Sales or inventory Valuation
2) An Option to Upload File from Desktop
3) An Option to retrieve file from Application Server
Note: Only one option out of 2 and 3 will be available.
Test Plan
[List test scenarios/cases to be executed here]
Test ID
|
Test Scenario
|
Expected Results
|
1
|
Input Retail Sales File and Run the Program
|
Program should Create 5 Journal Entries for Each Record and log Should be displayed
|
2
|
Input Inventory File and Run the Program
|
Program Should Create 2 journal Entries for Each Record and Log Should be displayed
|
Solution Details
[Provide complete technical details for configuration or programming here]
Retail Sales
A customized program is needed to create the journal entry. The program should call transaction FB50 to create one journal entry per store for the given period’s Retails Sales. Each journal entry will have different cost center and profit center assignment based on the store ID. Document type should be SA, and the Reference field should show the store ID.
1) If the Retail Pro transaction total amount for Total AR is positive number (more sales than return), below transaction should be created automatically:
- Dr: Accounts Receivable (GL account is different based on the Store ID, posting key 40)
Cost of Goods Sold (New 5* GL – TBD - posting key 40)
- Cr: Revenue (GL account 460000, posting key 50)
VAT (GL account 221020, posting key 50)
Inventory (New 13* GL – TBD - posting key 50)
2) If the Retail Pro transaction total amount for Total AR is negative number (more return than sales), below transaction should be created automatically:
- Dr: Revenue (GL account 460000, posting key 40)
VAT (GL account 221020, posting key 40)
Inventory (New 13* GL – TBD - posting key 40)
- Cr: Accounts Receivable (GL account is different based on the Store ID, posting key 50)
Cost of Goods Sold (New 5* GL – TBD - posting key 50)
This file should include all information that is needed for SAP journal entry creation for retail sales. SAP journal entry will record revenue, accounts receivables, Value Added Tax, Sales related inventory and cost of goods sold. The file will be sent via comma separated and the layout would be like below:
POS Transaction Category
|
Store Location
|
Posting Date
|
Currency
|
Net sales (excluding tax)
|
VAT
|
Total AR
|
Inventory change
|
COGS
|
Sales
|
TBD:UK001
|
04/21/2014
|
GBP
|
100
|
20
|
120
|
-39
|
39
|
Sales
|
TBD:GE001
|
04/21/2014
|
EUR
|
200
|
34
|
234
|
-78
|
-78
|
Inventory valuation
The program should call transaction FB50 to create one journal entry per store per inventory movement category. There will be 5 categories for Inventory related transactions. They are listed as below. Each category requires journal entry to be posted to different document type, cost center, trading partner and offset account based on the store ID and category. A customized mapping table maybe needed to achieve this goal.
01. Store Sales/Return
(NOTE!! If the movement type is 01, no journal entry is needed)
02. Goods Receipt from New Era Plant
03. Goods Return to New Era Plant
04. Sample
05. Cycle Count Adjustment
If the Retail Pro transaction total amount for Inventory is positive number, below transaction should be created automatically:
- Dr: Inventory (New 13* GL – TBD - posting key 40)
- Cr: Offset account (See above for the actual GL account ID for each category, posting key can be 50, 17 etc. based on the document type)
If the Retail Pro transaction total amount for Inventory is negative number, below transaction should be created automatically:
- Dr: Offset account (See above for the actual GL account ID for each category, posting key can be 40, 07 etc. based on the document type)
- Cr: Inventory (New 13* GL – TBD - posting key 50)
The file will be comma separated and the layout would be like below:
POS Transaction Category
|
Store Location
|
Posting Date
|
Currency
|
Inventory value
|
Movement type
|
Inventory
|
TBD:UK001
|
04/21/2014
|
GBP
|
-100
|
01
|
Inventory
|
TBD:UK001
|
04/21/2014
|
GBP
|
1000
|
02
|
Inventory
|
TBD:UK001
|
04/21/2014
|
GBP
|
-30
|
03
|
Inventory
|
TBD:UK001
|
04/21/2014
|
GBP
|
-5
|
04
|
Inventory
|
TBD:UK001
|
04/21/2014
|
GBP
|
-5
|
05
|
Inventory
|
TBD:UK002
|
04/21/2014
|
GBP
|
-100
|
01
|
Inventory
|
TBD:UK002
|
04/21/2014
|
GBP
|
1000
|
02
|
Inventory
|
TBD:UK002
|
04/21/2014
|
GBP
|
-300
|
03
|
Inventory
|
TBD:UK002
|
04/21/2014
|
GBP
|
-50
|
04
|
Inventory
|
TBD:UK002
|
04/21/2014
|
GBP
|
-50
|
05
|
|
|
|
|
|
|
Issues
[List Issues / Bugs identified in configuration or development]